chore: Check starters on CI + Remove 2332 port override #192
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
CI checks
To be more sure we're giving people working code to base their applications on, this PR adds a github workflow that run the following on CI for each starter:
New
package.json
scripts in starterspnpm check
: runs tsc (users can change it to do other checks too if desired)pnpm preview
: builds then runvite preview
No more port setting
We no longer set a port (2332) for the dev server - this was a remnant of where we started when building the sdk that we don't need anymore. This means
vite dev
will now use its own default port (5173), and that users can dopnpm dev --port <PORT>
to override this.dev:init
is now db agnosticAs long as a project has
migrate:dev
andseed
scripts in theirpackage.json
, we'll run them on postinstall (previously we only ran them if we found a prisma schema). This means the drizzle starter also only needspnpm i && pnpm dev
to get a running server